home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Almathera Ten Pack 2: CDPD 1
/
Almathera Ten on Ten - Disc 2: CDPD 1.iso
/
pd
/
051-075
/
074
/
tdebug
/
poster
next >
Wrap
Text File
|
1995-03-13
|
2KB
|
39 lines
Article 4281 of comp.sys.amiga:
Path: mcdsun!noao!hao!gatech!seismo!lll-lcc!styx!ames!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: DEVICE REQUEST INTERCEPT PROGRAM (Shar 1 of 1)
Message-ID: <8705040039.AA12386@cory.Berkeley.EDU>
Date: 4 May 87 00:39:34 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 509
This is version 1.00. It will give you most of the IO request
information for any device(s) you choose. It makes an assumption:
-(1) The device that it is monitoring doesn't go away while it's
monitoring it.
The program understands The trackdisk.device and will breakup the
Offset field into cylinder , track, and block number (sorry, currently
only prints the numbers right for the Amiga's Floppies).
TDEBUG works by intercepting the EXEC SendIO() and DoIO() vectors.
The new vector checks the sent request against the list of devices you want
displayed and places the IOStdReq part of the request in a FIFO (Allocating
a copy of the IOStdReq). It then signals the main program.
The Main program is constantly waiting for the latter signal, or
a BREAK (CTRL-C or CTRL-D). When it gets the signal, it checks the FIFO
and pulls off any pending buffers, displaying their contents and
deallocating the memory.
This is what I used to get those DOS statistics for you. It makes
an excellent debugging tool for devices since you can intercept any device.
Please mail all suggestions and comments to me.. remember, this is only
V1.00
-Matt